home *** CD-ROM | disk | FTP | other *** search
- Path: news.lpr.carel.fi!usenet
- From: Ari Lukumies <aril@cmt.lpr.mail.carel.fi>
- Newsgroups: comp.lang.c++
- Subject: Re: Incompatibility between BC4.5 32 bit DLL and MSVC 2.0 exe
- Date: Thu, 01 Feb 1996 12:47:10 +0200
- Organization: Carelcomp Forest
- Message-ID: <31109A2E.2808@cmt.lpr.mail.carel.fi>
- References: <4epure$k3p@idefix.eunet.fi>
- NNTP-Posting-Host: renoir.cclahti.carel.fi
- Mime-Version: 1.0
- Content-Type: text/plain; charset=us-ascii
- Content-Transfer-Encoding: 7bit
- X-Mailer: Mozilla 2.0b6a (WinNT; I)
-
- Planmeca Oy wrote:
- >
- > We have a "minor" problem. Part of our development team is developing
- > (32 bit) DLL:s with BC4.5 c++. Another part is developing the application
- > which needs to use that DLL. While trying to build the executable with
- > the LIB generated by BC for that DLL, MSVC complains: invalid or
- > corrupted library file.
- > We use C (not C++) interface between the EXE and the DLL.
- >
- > The same approach works with 16 bit EXE and 16 bit DLL. Is there anything
- > to do?
-
- I haven't used BC4.5 so this may not be correct, but what comes to MS compilers, they use
- COFF format for object files (and libraries), and it might be that Borland doesn't. For
- 16-bit objects, they both use the Intel Relocatable Module Format with Microsoft/Borland
- extensions. Also, the way to store symbolic information differs. You would want to check
- the compile/link switches and modes.
-
- Later,
- AriL
- --
- All my opinions are mine and mine alone.
-